|
|
 |
|
|
|
|
ROI (return on investment), 224, 474 |
|
|
|
|
|
|
|
|
Role classes, 296-297, 303-305, 309, 330, 374 |
|
|
|
|
|
|
|
|
Role object, 304 |
|
|
|
|
|
|
|
|
role-form couplings, 297 |
|
|
|
|
|
|
|
|
RoleID property, 296, 305 |
|
|
|
|
|
|
|
|
roles |
|
|
|
|
|
|
|
|
BankTellerRole, 303 |
|
|
|
|
|
|
|
|
displaying task captions for, 297 |
|
|
|
|
|
|
|
|
ManagerRole, 303 |
|
|
|
|
|
|
|
|
sequences, 299 |
|
|
|
|
|
|
|
|
versus users, 293 |
|
|
|
|
|
|
|
|
workgroup, 299 |
|
|
|
|
|
|
|
|
rollbacks, 300 |
|
|
|
|
|
|
|
|
routing, 294, 304 |
|
|
|
|
|
|
|
|
ad hoc, 298 |
|
|
|
|
|
|
|
|
dynamic, 298 |
|
|
|
|
|
|
|
|
parallel, 292 |
|
|
|
|
|
|
|
|
workgroup queues, 299 |
|
|
|
|
|
|
|
|
WorkMessenger example, 294-295 |
|
|
|
|
|
|
|
|
rows |
|
|
|
|
|
|
|
|
length, 378 |
|
|
|
|
|
|
|
|
random access files, 377 |
|
|
|
|
|
|
|
|
rules (business) |
|
|
|
|
|
|
|
|
differences from policies, 338 |
|
|
|
|
|
|
|
|
discovering, 340 |
|
|
|
|
|
|
|
|
encapsulating, 343 |
|
|
|
|
|
|
|
|
enforcing, 344 |
|
|
|
|
|
|
|
|
GUI, 338 |
|
|
|
|
|
|
|
|
testing, 177 |
|
|
|
|
|
|
|
|
violations, 344 |
|
|
|
|
|
|
|
|
Rumbaugh, Jim, 37 |
|
|
|
|
|
|
|
|
runtime errors |
|
|
|
|
|
|
|
|
debugging, 23, 185 |
|
|
|
|
|
|
|
|
logging, 188 |
|
|
|
|
|
|
|
|
object management, 112-114 |
|
|
|
|
|
|
|
|
trapping, 173 |
|
|
|
|
|
|
|
|
SA/SD (Structured Analysis/Structured Design), 9 |
|
|
|
|
|
|
|
|
sabotage, protecting against, 291 |
|
|
|
|
|
|
|
|
Samsona Bank Teller System |
|
|
|
|
|
|
|
|
architecture, 104 |
|
|
|
|
|
|
|
|
BankAccountProduct class, 343 |
|
|
|
|
|
|
|
|
banking |
|
|
|
|
|
|
|
|
file management processes, 386-388 |
|
|
|
|
|
|
|
|
products, 340 |
|
|
|
|
|
|
|
|
typical classes, 340-342 |
|
|
|
|
|
|
|
|
BankTellerRole role, 303 |
|
|
|
|
|
|
|
|
BankTransaction user-defined type (UDT), 383 |
|
|
|
|
|
|
|
|
BankTransactionPolicy package, 342-344 |
|
|
|
|
|
|
|
|
Business Rules Subsystem, 345-347 |
|
|
|
|
|
|
|
|
classes, 105-106 |
|
|
|
|
|
|
|
|
code generation, 107 |
|
|
|
|
|
|
|
|
collections |
|
|
|
|
|
|
|
|
assigning, 106-107 |
|
|
|
|
|
|
|
|
building, 106 |
|
|
|
|
|
|
|
|
Database Access Subsystem, 430, 435 |
|
|
|
|
|
|
|
|
deploying, 462 |
|
|
|
|
|
|
|
|
development, 42-43 |
|
|
|
|
|
|
|
|
Elaboration Phase, 229-234 |
|
|
|
|
|
|
|
|
error handling, 405-408 |
|
|
|
|
|
|
|
|
File Operations Subsystem implementation, 388-392 |
|
|
|
|
|
|
|
|
GUI |
|
|
|
|
|
|
|
|
controller objects, 271-275 |
|
|
|
|
|
|
|
|
designing, 264 |
|
|
|
|
|
|
|
|
Facade design pattern, 275-276 |
|
|
|
|
|
|
|
|
frmAccountDetail form, 267 |
|
|
|
|
|
|
|
|
frmMaintainAccount form, 269 |
|
|
|
|
|
|
|
|
frmMaintainBankProducts form, 269 |
|
|
|
|
|
|
|
|
frmMaintainCustomer form, 269 |
|
|
|
|
|
|
|
|
frmMaintainUsers form, 269 |
|
|
|
|
|
|
|
|
frmMaintainWorkgroups form, 270 |
|
|
|
|
|
|
|
|
frmMDI form, 266, 280-281 |
|
|
|
|
|
|
|
|
implementation guidelines, 264 |
|
|
|
|
|
|
|
|
scenario scripts, 265 |
|
|
|
|
|
|
|
|
use case, 266-268 |
|
|
|
|
|
|
|
|
Internal Application Manager Subsystem, 324-328 |
|
|
|
|
|
|
|
|
iteration plan, 217-218 |
|
|
|
|
|
|
|
|
problem statements, 218-222 |
|
|
|
|
|
|
|
|
project development/management scenario, 466-467 |
|
|
|
|
|
|
|
|
Reporting/Printing Subsystem, 365-367 |
|
|
|
|
|
|
|
|
scenarios, 52-57 |
|
|
|
|
|
|
|
|
subsystems, 209 |
|
|
|
|
|
|
|
|
test components, 143-148 |
|
|
|
|
|
|
|
|
see also Second Bank of Carrollton example |
|
|
|
|
|
|
|
|
San Francisco project, 461 |
|
|
|
|
|
|
|
|
saveAllCustomers method, 366 |
|
|
|
|
|
|
|
|
SaveFile method (Rich Text Box), 189 |
|
|
|
|
|